Add the Beasts TypeScript SDK and the self-service registration app - #21

The Connect button called `connect({ connector: connectors[0] })` with
Controller as the only option and no error handling, so any failure was
invisible — the button simply appeared dead.

- Wallet picker listing Controller alongside injected wallets. Ready
  (formerly Argent) and Braavos are surfaced as recommended even when not
  installed, so the choice is visible rather than hidden.
- `useInjectedConnectors` scans window.starknet, so connector construction
  moved into a WalletProvider component that renders StarknetConfig.
- Connection failures are shown in the modal. A wallet whose extension is
  absent is disabled and labelled "Not detected" rather than silently
  doing nothing when clicked.
- Footer now names the network, so which chain the app is pointed at is
  never a guess.

Also fixes the connect-modal styles landing in src/styles.css at the repo
root instead of app/src/styles.css, which left the modal rendering as an
unstyled full-width block below the page content.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

A percentage height against an `aspect-ratio` parent resolves to `auto`, so
a square Beast sized itself from its own 1:1 ratio instead of the frame's:
a 32x32 image rendered 268x268 inside a 268x175 box and `overflow: hidden`
cropped the top and bottom. Artists saw a horizontal slice of their work.

Absolute inset gives the image a definite box to fit inside, so
`object-fit: contain` scales the whole thing down and centres it — matching
the contract's own layout, which draws a square art region inside a wider
frame.

The smoke test now uploads a 32x32 fixture with a border on all four sides
and asserts the rendered image fits its frame. The border is the tell: any
crop loses an edge.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Manage was the submit button of a species-number input, so it did nothing
unless you already knew your ID. It now opens a list of everything the
connected wallet controls, each card linking into the existing dashboard.
Lookup-by-ID survives inside that view for anyone who does know the number.

The list keys off the artist role, not the Genesis Beast. The two start
together but diverge the moment either is transferred, and the role is what
the registry's permissioned entrypoints check — listing by token would
offer controls that revert.

SDK gains getSpeciesByArtist / getOwnedSpecies, derived from
BeastRegistered and ArtistTransferred events rather than by scanning IDs:
the registry keeps no artist index and species_count grows without bound.

BeastsAddresses gains a required fromBlock, which is a correctness fix
rather than an optimisation. Public nodes cap how far back getEvents will
look, and the one used here answers an over-wide range with an EMPTY
RESULT rather than an error — so scanning from genesis reports "this
wallet owns nothing" instead of failing. Sepolia is anchored to the
set_nft_address block, a provably safe floor: the registry rejects every
registration until the NFT is wired, so no BeastRegistered can predate it.

Live tests assert the lookup returns something, which is the guard against
that failure mode being silent again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

The artist role is now ownership of the species' Genesis Beast, and the
collection exposes token_of_owner_by_index — so listing what a wallet
controls is a walk of its own tokens plus a local decode. A Genesis Beast
is any token with no affixes, and a token ID already carries its species.

That deletes the event scan and, with it, BeastsAddresses.fromBlock: the
whole silent-empty-range hazard was a consequence of needing events at all.

Transferring a species is now an ERC721 transfer of the creator token.
transferArtistRoleCall is replaced by transferGenesisBeastCall, and the
dashboard panel says plainly that sending the token sends every control on
the page — because a marketplace sale does exactly the same thing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

The verification table still carried the provider from the superseded
deployment. Each species gets its own instance, salted by species ID, so a
redeploy of the registry changes it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Three views the app was missing, all reachable by URL:

- /collection/0xabc… — every Beast an address holds. The address is a route
  parameter, not component state, so it can be edited to any wallet and
  shared; viewing someone else's collection needs no connection.
- /beasts — the bestiary, one card per species. Grouped by default because
  the collection is unbounded and one species can hold 1,243 Beasts; a flat
  list of tokens would be unreadable long before it was useful.
- /beasts/:id — every Beast of a species, strongest first, read from the
  contract's own per-species rank list rather than by scanning.

Routing is hash-based so every page is a real URL on a static host without
server rewrites.

SDK: getArt now mirrors the contract's own routing and resolves genesis
species through the four legacy art contracts, so the original 75 render
too. Adds species summaries, wallet token enumeration and per-species token
listing.

Art is fetched per Beast rather than per species: a community provider
receives the whole decoded Beast and may vary art by affix, tier or level,
so caching by species would show the wrong picture for exactly the providers
that make the interface worth having.

A tile whose art will not decode now says so instead of rendering a broken
image. The contract checks media type, base64 and magic bytes, but nothing
on chain can prove a payload is a real image.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>